Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de00b19ae6e3c4a9edcb883e11ca26941cce1e94e0a10b480c132ce28d3534b3

Tx prefix hash: bc0339da07d25560ff513a32d32a25adabc3d79e0c3ab2cb1c12481e7d8bbf34
Tx public key: 2042213a48da7a5eccbd9adc1e95aa2cc81acc57597e3ad0ef105b8a0b4e624d
Timestamp: 1648339998 Timestamp [UCT]: 2022-03-27 00:13:18 Age [y:d:h:m:s]: 02:354:00:29:40
Block: 467116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 772368 RingCT/type: yes/0
Extra: 012042213a48da7a5eccbd9adc1e95aa2cc81acc57597e3ad0ef105b8a0b4e624d0211000000102e6b1fd5000000000000000000

1 output(s) for total of 17.388056256000 dcy

stealth address amount amount idx
00: b458d3ae14955b58f24242cc07617be3ed6a0102e95e7ae342fd1d877bd80630 17.388056256000 885563 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": 467126, "vin": [ { "gen": { "height": 467116 } } ], "vout": [ { "amount": 17388056256, "target": { "key": "b458d3ae14955b58f24242cc07617be3ed6a0102e95e7ae342fd1d877bd80630" } } ], "extra": [ 1, 32, 66, 33, 58, 72, 218, 122, 94, 204, 189, 154, 220, 30, 149, 170, 44, 200, 26, 204, 87, 89, 126, 58, 208, 239, 16, 91, 138, 11, 78, 98, 77, 2, 17, 0, 0, 0, 16, 46, 107, 31, 213, 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