Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe2e083688d6635eb9b59d95b6d996c3ac336ead84141eb02ee896200bf09f05

Tx prefix hash: 2bcb5d879931e2ed5aefb59bf3944ad25d6c5cbe259c71e6d0109f436ff693bd
Tx public key: d74fdaf49f7f680600c1c00eb318a0e53bb67f308b59458298b5e3e1e8a0221c
Timestamp: 1732176827 Timestamp [UCT]: 2024-11-21 08:13:47 Age [y:d:h:m:s]: 00:038:09:42:33
Block: 1158404 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27478 RingCT/type: yes/0
Extra: 01d74fdaf49f7f680600c1c00eb318a0e53bb67f308b59458298b5e3e1e8a0221c021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d48756a892b01e43cc1e104cf6b44f38e4ee18644a0d3a09eff56c561005b61 0.600000000000 1644033 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": 1158414, "vin": [ { "gen": { "height": 1158404 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d48756a892b01e43cc1e104cf6b44f38e4ee18644a0d3a09eff56c561005b61" } } ], "extra": [ 1, 215, 79, 218, 244, 159, 127, 104, 6, 0, 193, 192, 14, 179, 24, 160, 229, 59, 182, 127, 48, 139, 89, 69, 130, 152, 181, 227, 225, 232, 160, 34, 28, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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