Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42870dcc921574d3a4bcd2d3fc276475ff6e4d3a97758a43ab276e13c22f7a5c

Tx prefix hash: 0efae2e83c3eb61473f2bf9495062aa15305f99470006c3c8676c23a5ed972dd
Tx public key: 5f49bd6fd0b49564c171826a19199e537dc18498ea13e8074cefe86b65bd99ed
Timestamp: 1703901437 Timestamp [UCT]: 2023-12-30 01:57:17 Age [y:d:h:m:s]: 01:318:17:08:48
Block: 924089 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 486620 RingCT/type: yes/0
Extra: 015f49bd6fd0b49564c171826a19199e537dc18498ea13e8074cefe86b65bd99ed02110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6cecd98bfba05e5e4bc10e88f81efb7b7ed52fb7d69b8a78fca1a4e04960b828 0.600000000000 1381831 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": 924099, "vin": [ { "gen": { "height": 924089 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6cecd98bfba05e5e4bc10e88f81efb7b7ed52fb7d69b8a78fca1a4e04960b828" } } ], "extra": [ 1, 95, 73, 189, 111, 208, 180, 149, 100, 193, 113, 130, 106, 25, 25, 158, 83, 125, 193, 132, 152, 234, 19, 232, 7, 76, 239, 232, 107, 101, 189, 153, 237, 2, 17, 0, 0, 0, 10, 122, 156, 244, 199, 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