Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 869eb6cc7823adfee3e4a289fc7768dd198a4b578ff1cac958bf049def76ecd2

Tx prefix hash: be2c0a142f2f3ba0cec996a7ae137b1823a52ff143b1f9e2bf2703024d184e1a
Tx public key: 42144f12d29c0343c6b3129656e2a1222e76001f6520cb66680ae20e13d908b1
Timestamp: 1760514505 Timestamp [UCT]: 2025-10-15 07:48:25 Age [y:d:h:m:s]: 00:082:14:20:40
Block: 1390331 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59151 RingCT/type: yes/0
Extra: 0142144f12d29c0343c6b3129656e2a1222e76001f6520cb66680ae20e13d908b1021100000009df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 136dead2fd0475f77255a2d6e58322d9a1dc0edec434a7fdd017d786b4ae87de 0.600000000000 1878572 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": 1390341, "vin": [ { "gen": { "height": 1390331 } } ], "vout": [ { "amount": 600000000, "target": { "key": "136dead2fd0475f77255a2d6e58322d9a1dc0edec434a7fdd017d786b4ae87de" } } ], "extra": [ 1, 66, 20, 79, 18, 210, 156, 3, 67, 198, 179, 18, 150, 86, 226, 161, 34, 46, 118, 0, 31, 101, 32, 203, 102, 104, 10, 226, 14, 19, 217, 8, 177, 2, 17, 0, 0, 0, 9, 223, 90, 36, 122, 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