Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e45ff5115ec5d1a220997dde7e7da9267c02b4dcba69b12a330be40c8491640

Tx prefix hash: bedcf798c37b287fc5f4315406717328d83cbede4206ff0039e23f2288561e6e
Tx public key: aa663f29df49f325bb6a19dc3836daae333f441dde40abe8b4ac38507a7dfcb5
Timestamp: 1701380814 Timestamp [UCT]: 2023-11-30 21:46:54 Age [y:d:h:m:s]: 01:126:18:30:04
Block: 903192 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351759 RingCT/type: yes/0
Extra: 01aa663f29df49f325bb6a19dc3836daae333f441dde40abe8b4ac38507a7dfcb502110000000146113aa8000000000000000000

1 output(s) for total of 0.624237637000 dcy

stealth address amount amount idx
00: fa8c48edb6ec92c69ba60beeaed47528bbd72b0a47aa9e1ef8903b35a5048ce6 0.624237637000 1359863 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": 903202, "vin": [ { "gen": { "height": 903192 } } ], "vout": [ { "amount": 624237637, "target": { "key": "fa8c48edb6ec92c69ba60beeaed47528bbd72b0a47aa9e1ef8903b35a5048ce6" } } ], "extra": [ 1, 170, 102, 63, 41, 223, 73, 243, 37, 187, 106, 25, 220, 56, 54, 218, 174, 51, 63, 68, 29, 222, 64, 171, 232, 180, 172, 56, 80, 122, 125, 252, 181, 2, 17, 0, 0, 0, 1, 70, 17, 58, 168, 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