Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8dcb314996290ad41462836e8c13cc5d87a7d0f4edeb5fb47ac832071646f061

Tx prefix hash: e671dfa3390902878344a9a449167016b45b244c67bb7a626e0959bc7e8cf0cb
Tx public key: 3975742a9a4a3aef2b089e4583440bda7c1081d70aeab17aeb55c4422fd52bd5
Timestamp: 1734797586 Timestamp [UCT]: 2024-12-21 16:13:06 Age [y:d:h:m:s]: 00:100:18:17:10
Block: 1180148 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71763 RingCT/type: yes/0
Extra: 013975742a9a4a3aef2b089e4583440bda7c1081d70aeab17aeb55c4422fd52bd502110000000f007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b2fe4f8815d18e763f84fe4120b62a33331923023de5bec137b1a9612f11a7f 0.600000000000 1666553 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": 1180158, "vin": [ { "gen": { "height": 1180148 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b2fe4f8815d18e763f84fe4120b62a33331923023de5bec137b1a9612f11a7f" } } ], "extra": [ 1, 57, 117, 116, 42, 154, 74, 58, 239, 43, 8, 158, 69, 131, 68, 11, 218, 124, 16, 129, 215, 10, 234, 177, 122, 235, 85, 196, 66, 47, 213, 43, 213, 2, 17, 0, 0, 0, 15, 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