Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0044c9dc50d8585ecc51a112f395bb95565b1ae3e17a36aceeb84bc0d5c9ae5b

Tx prefix hash: ff867eaf43b48153ba86db8a8bb221c47d7e71f407cf6e05a7985cbdcbade035
Tx public key: 1b7c8f2e3b8a60088f4919e9a1661feabe1fd593813931edeea2b1ab559a87a5
Timestamp: 1713598611 Timestamp [UCT]: 2024-04-20 07:36:51 Age [y:d:h:m:s]: 01:015:20:54:55
Block: 1004463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272315 RingCT/type: yes/0
Extra: 011b7c8f2e3b8a60088f4919e9a1661feabe1fd593813931edeea2b1ab559a87a50211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 817b3623131c5ed4cef11db9d128320aacadefcd774c4e548e989cdd212ae02d 0.600000000000 1465031 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": 1004473, "vin": [ { "gen": { "height": 1004463 } } ], "vout": [ { "amount": 600000000, "target": { "key": "817b3623131c5ed4cef11db9d128320aacadefcd774c4e548e989cdd212ae02d" } } ], "extra": [ 1, 27, 124, 143, 46, 59, 138, 96, 8, 143, 73, 25, 233, 161, 102, 31, 234, 190, 31, 213, 147, 129, 57, 49, 237, 238, 162, 177, 171, 85, 154, 135, 165, 2, 17, 0, 0, 0, 1, 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