Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e9d4ba19bd06bcc323930a1f9e4df35430811396772976ea83fc8ca8f310f3b

Tx prefix hash: 0e30a93fc791847a620b4e23406fc0b68ea2ff6b0080edb968483ef8fbe9ca93
Tx public key: b410dfe5025dc0f6f1e80e0471cbedb772d84337e457eec0a55346cb300fd4c1
Timestamp: 1694630506 Timestamp [UCT]: 2023-09-13 18:41:46 Age [y:d:h:m:s]: 01:208:06:02:30
Block: 847420 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 409926 RingCT/type: yes/0
Extra: 01b410dfe5025dc0f6f1e80e0471cbedb772d84337e457eec0a55346cb300fd4c1021100000005faf35c9c000000000000000000

1 output(s) for total of 0.955313290000 dcy

stealth address amount amount idx
00: 91eb0fe2663bf53f3585d936a0efa35f87a0cee45654b808d3e5336d8794cb1c 0.955313290000 1300940 of 0

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": 847430, "vin": [ { "gen": { "height": 847420 } } ], "vout": [ { "amount": 955313290, "target": { "key": "91eb0fe2663bf53f3585d936a0efa35f87a0cee45654b808d3e5336d8794cb1c" } } ], "extra": [ 1, 180, 16, 223, 229, 2, 93, 192, 246, 241, 232, 14, 4, 113, 203, 237, 183, 114, 216, 67, 55, 228, 87, 238, 192, 165, 83, 70, 203, 48, 15, 212, 193, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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