Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01d088837f88e0b52a09b13f0da50b702870d6c1759a104a78c6d53859e15966

Tx prefix hash: 94d423203054de12fa5c0621cd27f071826bb17e403b5d999e2d6871ea06f94d
Tx public key: decd2c7127f9cbee4d42023f546a2d2030b1e8ccbce700e732a1be769be202d2
Timestamp: 1703168571 Timestamp [UCT]: 2023-12-21 14:22:51 Age [y:d:h:m:s]: 01:185:15:45:47
Block: 918009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393619 RingCT/type: yes/0
Extra: 01decd2c7127f9cbee4d42023f546a2d2030b1e8ccbce700e732a1be769be202d20211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 636c15beb8933d8cde9c754e0b8b102f418f4b6cb1efbded24f591ad7b7444c9 0.600000000000 1375645 of 15

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": 918019, "vin": [ { "gen": { "height": 918009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "636c15beb8933d8cde9c754e0b8b102f418f4b6cb1efbded24f591ad7b7444c9" } } ], "extra": [ 1, 222, 205, 44, 113, 39, 249, 203, 238, 77, 66, 2, 63, 84, 106, 45, 32, 48, 177, 232, 204, 188, 231, 0, 231, 50, 161, 190, 118, 155, 226, 2, 210, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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