Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 402165babe924a5c4a7dd754fcaa2fa9e5671a377a01529b276ccb8ccd82fa76

Tx prefix hash: 462a697e1a48461212ed3868dca7009577a3cac5ebc7ee026c62f6cfa2a38584
Tx public key: b4295465ea214fd072301b2d8e7593abcd042494f0fdd0ec782b22d1e394bbc8
Timestamp: 1738332986 Timestamp [UCT]: 2025-01-31 14:16:26 Age [y:d:h:m:s]: 00:336:20:05:39
Block: 1209122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238570 RingCT/type: yes/0
Extra: 01b4295465ea214fd072301b2d8e7593abcd042494f0fdd0ec782b22d1e394bbc8021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7cb798988ae117ecd381b9a5d10985143feb71fc571185d6dbfa316d1dbc9b0 0.600000000000 1695863 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": 1209132, "vin": [ { "gen": { "height": 1209122 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7cb798988ae117ecd381b9a5d10985143feb71fc571185d6dbfa316d1dbc9b0" } } ], "extra": [ 1, 180, 41, 84, 101, 234, 33, 79, 208, 114, 48, 27, 45, 142, 117, 147, 171, 205, 4, 36, 148, 240, 253, 208, 236, 120, 43, 34, 209, 227, 148, 187, 200, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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