Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3eb4c81918831b818e195097c9c1415c3da4054ced00b60480a9fc369b202cbc

Tx prefix hash: 6e4dc1f72b9a9de15af997ee77bdea633bf9e7713f261a97023f2ede754a1508
Tx public key: 4a069c8c5c05c154df6047db3126c5e9ffd450ae221b7f2ab881bd2a6b760d97
Timestamp: 1711811473 Timestamp [UCT]: 2024-03-30 15:11:13 Age [y:d:h:m:s]: 01:307:20:01:44
Block: 989695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 478592 RingCT/type: yes/0
Extra: 014a069c8c5c05c154df6047db3126c5e9ffd450ae221b7f2ab881bd2a6b760d970211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1efa5e1d83fcbed2f3ae103f36c232e813fb53e8f2dfe8a19a2e8b8309a5a841 0.600000000000 1450013 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": 989705, "vin": [ { "gen": { "height": 989695 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1efa5e1d83fcbed2f3ae103f36c232e813fb53e8f2dfe8a19a2e8b8309a5a841" } } ], "extra": [ 1, 74, 6, 156, 140, 92, 5, 193, 84, 223, 96, 71, 219, 49, 38, 197, 233, 255, 212, 80, 174, 34, 27, 127, 42, 184, 129, 189, 42, 107, 118, 13, 151, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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