Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 408557e978bd11a286a89d2cf19304dde5a2bd61dc425797c7c324049335234a

Tx prefix hash: cfdcd09cadc2144d9a658e1f28cb5bf8c4a0b91b941aa25528ce6bb2daa1a321
Tx public key: 4ff08e027188d0767cd675f9f7df9f641c73e6979ac23619b5ed40f5dafd4a17
Timestamp: 1719153783 Timestamp [UCT]: 2024-06-23 14:43:03 Age [y:d:h:m:s]: 00:322:07:10:47
Block: 1050524 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230345 RingCT/type: yes/0
Extra: 014ff08e027188d0767cd675f9f7df9f641c73e6979ac23619b5ed40f5dafd4a1702110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aee272316cf93df98001c6b34886bd77983b7f1657c107f4324fad268ac4c76e 0.600000000000 1520699 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": 1050534, "vin": [ { "gen": { "height": 1050524 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aee272316cf93df98001c6b34886bd77983b7f1657c107f4324fad268ac4c76e" } } ], "extra": [ 1, 79, 240, 142, 2, 113, 136, 208, 118, 124, 214, 117, 249, 247, 223, 159, 100, 28, 115, 230, 151, 154, 194, 54, 25, 181, 237, 64, 245, 218, 253, 74, 23, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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