Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c23c1449b89ad71591ee90ac23e9fd2ad96f4da366782961f1db22b306c9d935

Tx prefix hash: 5b6cfb659edd25238c5d85b6744ec0f27490ff70cc84008e8e61f254381c6a5a
Tx public key: d9a580f8b38e58191b5076fad9c09236c32c66b53d5dcd872f5aa3bb6b4358ac
Timestamp: 1708923778 Timestamp [UCT]: 2024-02-26 05:02:58 Age [y:d:h:m:s]: 01:256:07:25:55
Block: 965734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 441906 RingCT/type: yes/0
Extra: 01d9a580f8b38e58191b5076fad9c09236c32c66b53d5dcd872f5aa3bb6b4358ac0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc96e1c0225fdffdb17bd2a34669afc19193e1dc461655064b5cd178e7a5a13b 0.600000000000 1425489 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": 965744, "vin": [ { "gen": { "height": 965734 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc96e1c0225fdffdb17bd2a34669afc19193e1dc461655064b5cd178e7a5a13b" } } ], "extra": [ 1, 217, 165, 128, 248, 179, 142, 88, 25, 27, 80, 118, 250, 217, 192, 146, 54, 195, 44, 102, 181, 61, 93, 205, 135, 47, 90, 163, 187, 107, 67, 88, 172, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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