Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f530a4f3c4063f42403197bedf3be4d67d67b85d442b91dcac300071944b2233

Tx prefix hash: 098330fc68b398887a4f1f039b60bb9626b0f93ff5a2ed193e51f21abb991471
Tx public key: e5981d021b3be1c9a416b2c9b9cb7cbc82a07032584e05e0351df702d28998df
Timestamp: 1632814783 Timestamp [UCT]: 2021-09-28 07:39:43 Age [y:d:h:m:s]: 03:100:20:40:40
Block: 342357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 848856 RingCT/type: yes/0
Extra: 01e5981d021b3be1c9a416b2c9b9cb7cbc82a07032584e05e0351df702d28998df02110000002cfdc024ec000000000000000000

1 output(s) for total of 45.043234707000 dcy

stealth address amount amount idx
00: 3fdff88b0075af88db75cfdc3872e63fce04ad621397a4b282b1f136c52544d6 45.043234707000 703059 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": 342367, "vin": [ { "gen": { "height": 342357 } } ], "vout": [ { "amount": 45043234707, "target": { "key": "3fdff88b0075af88db75cfdc3872e63fce04ad621397a4b282b1f136c52544d6" } } ], "extra": [ 1, 229, 152, 29, 2, 27, 59, 225, 201, 164, 22, 178, 201, 185, 203, 124, 188, 130, 160, 112, 50, 88, 78, 5, 224, 53, 29, 247, 2, 210, 137, 152, 223, 2, 17, 0, 0, 0, 44, 253, 192, 36, 236, 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