Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 996a0374b656b81afec373b2fbb037c8c112df5035f5e9940ad8f815415a037b

Tx prefix hash: 3fb3cdf51f6e3b89956d990c5ced42b19ca11be6e73966e91e3022b91ade683b
Tx public key: a696b87666b2a739041cbaac1cf0f6d8e6ad0e05d427cf2566b4a8afe46b3104
Timestamp: 1673206980 Timestamp [UCT]: 2023-01-08 19:43:00 Age [y:d:h:m:s]: 02:021:04:25:13
Block: 670474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 536803 RingCT/type: yes/0
Extra: 01a696b87666b2a739041cbaac1cf0f6d8e6ad0e05d427cf2566b4a8afe46b310402110000000252542ceb000000000000000000

1 output(s) for total of 3.685032034000 dcy

stealth address amount amount idx
00: ee9d2bac55e7f30d3144ac13f69e3454635ff69b578a5d70ec408677484a37e1 3.685032034000 1111879 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": 670484, "vin": [ { "gen": { "height": 670474 } } ], "vout": [ { "amount": 3685032034, "target": { "key": "ee9d2bac55e7f30d3144ac13f69e3454635ff69b578a5d70ec408677484a37e1" } } ], "extra": [ 1, 166, 150, 184, 118, 102, 178, 167, 57, 4, 28, 186, 172, 28, 240, 246, 216, 230, 173, 14, 5, 212, 39, 207, 37, 102, 180, 168, 175, 228, 107, 49, 4, 2, 17, 0, 0, 0, 2, 82, 84, 44, 235, 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