Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 151f5e24b838f113fee8472f3011d55ddd52a02a408857ac252d4f813da418b9

Tx prefix hash: 8b723ff39eb9fc3ac4dabc963c21f3cb3cf1b33636ee86061820fe54f9400c59
Tx public key: 9c3fd43a7a9af193ada68e84a914aa76fecb647382f57278b045ab8a22595901
Timestamp: 1698250281 Timestamp [UCT]: 2023-10-25 16:11:21 Age [y:d:h:m:s]: 01:165:03:01:29
Block: 877454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379005 RingCT/type: yes/0
Extra: 019c3fd43a7a9af193ada68e84a914aa76fecb647382f57278b045ab8a225959010211000000024b8f5122000000000000000000

1 output(s) for total of 0.759679953000 dcy

stealth address amount amount idx
00: 543f87d75b53ce1881c53a22fd2c4a12293096fc973229fd1165dd72f025f8d3 0.759679953000 1332830 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": 877464, "vin": [ { "gen": { "height": 877454 } } ], "vout": [ { "amount": 759679953, "target": { "key": "543f87d75b53ce1881c53a22fd2c4a12293096fc973229fd1165dd72f025f8d3" } } ], "extra": [ 1, 156, 63, 212, 58, 122, 154, 241, 147, 173, 166, 142, 132, 169, 20, 170, 118, 254, 203, 100, 115, 130, 245, 114, 120, 176, 69, 171, 138, 34, 89, 89, 1, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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