Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c48ba6f45fb1cfad970ceeb021c90a12434261d71ec4c431b35428b53712527

Tx prefix hash: 51752d2d65c054d8178b24893243a6e75645273a2938eb98afbf4a58a4640939
Tx public key: b3bd6c7a2513e8e64e3c55ebd00c9d2b89540952320b2974aa8b53f62a3b1387
Timestamp: 1729171282 Timestamp [UCT]: 2024-10-17 13:21:22 Age [y:d:h:m:s]: 00:097:04:39:28
Block: 1133592 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69427 RingCT/type: yes/0
Extra: 01b3bd6c7a2513e8e64e3c55ebd00c9d2b89540952320b2974aa8b53f62a3b1387021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60c99b142e1625bd3881f66263eb66859555cfa4ab3376bd96cf4d7a2e4f944f 0.600000000000 1616759 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": 1133602, "vin": [ { "gen": { "height": 1133592 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60c99b142e1625bd3881f66263eb66859555cfa4ab3376bd96cf4d7a2e4f944f" } } ], "extra": [ 1, 179, 189, 108, 122, 37, 19, 232, 230, 78, 60, 85, 235, 208, 12, 157, 43, 137, 84, 9, 82, 50, 11, 41, 116, 170, 139, 83, 246, 42, 59, 19, 135, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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