Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f2b0a804137c54797105ca16bfedef9c5fe56a741fdbafcf02776b2cb756c47

Tx prefix hash: f5bfb14ac2318ce7d9d780f275a2124bc9548f2ddca654534cb8507bff215f0e
Tx public key: fa4e905f364c8a8474db96fe4e2384ce1d35812785da2231633f1ffb421547f4
Timestamp: 1647758249 Timestamp [UCT]: 2022-03-20 06:37:29 Age [y:d:h:m:s]: 02:330:19:45:46
Block: 462350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 755723 RingCT/type: yes/0
Extra: 01fa4e905f364c8a8474db96fe4e2384ce1d35812785da2231633f1ffb421547f402110000000fd3fcec30000000000000000000

1 output(s) for total of 18.031953554000 dcy

stealth address amount amount idx
00: bfde08fe71cc603c01900f79c3c06e30bf9efd85e30a0efba9e8b99a0d3ad67c 18.031953554000 879787 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": 462360, "vin": [ { "gen": { "height": 462350 } } ], "vout": [ { "amount": 18031953554, "target": { "key": "bfde08fe71cc603c01900f79c3c06e30bf9efd85e30a0efba9e8b99a0d3ad67c" } } ], "extra": [ 1, 250, 78, 144, 95, 54, 76, 138, 132, 116, 219, 150, 254, 78, 35, 132, 206, 29, 53, 129, 39, 133, 218, 34, 49, 99, 63, 31, 251, 66, 21, 71, 244, 2, 17, 0, 0, 0, 15, 211, 252, 236, 48, 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