Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: a6304a03b9fba54a843d28424aee838f94e9ae62628c6324e7f85d02ce43f15b

Tx prefix hash: 7970d4be8ee699ab8a73fe31519d25c4312f9a58ea5716b9e38138f98a7a5067
Tx public key: 9f18da9de0d01feabb6863861deb8ad27ffc8d0f41ab1c43d28b0bbdaaab26af
Timestamp: 1688703991 Timestamp [UCT]: 2023-07-07 04:26:31 Age [y:d:h:m:s]: 01:288:04:43:08
Block: 798361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 467108 RingCT/type: yes/0
Extra: 019f18da9de0d01feabb6863861deb8ad27ffc8d0f41ab1c43d28b0bbdaaab26af02110000000533af99f4000000000000000000

1 output(s) for total of 1.388988736000 dcy

stealth address amount amount idx
00: e53cc6bfff437be3137925145d17d5aec4fb977063e12c13edf81c4464a1f9e1 1.388988736000 1249294 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 798371, "vin": [ { "gen": { "height": 798361 } } ], "vout": [ { "amount": 1388988736, "target": { "key": "e53cc6bfff437be3137925145d17d5aec4fb977063e12c13edf81c4464a1f9e1" } } ], "extra": [ 1, 159, 24, 218, 157, 224, 208, 31, 234, 187, 104, 99, 134, 29, 235, 138, 210, 127, 252, 141, 15, 65, 171, 28, 67, 210, 139, 11, 189, 170, 171, 38, 175, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8