Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cfccc4af9c41b8d4fd955a739d5e13d63b16439599736d6e79aa41269987349

Tx prefix hash: dc6a0b7562defe2382fb90fdd8487f5f0c8b88be2a5626ad1d0245f17a49ace0
Tx public key: 43622a09d60b91206a2e05a0c0e9e7a9892a319f66029bc2e659500cdc28b227
Timestamp: 1731832221 Timestamp [UCT]: 2024-11-17 08:30:21 Age [y:d:h:m:s]: 00:121:04:58:09
Block: 1155551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86461 RingCT/type: yes/0
Extra: 0143622a09d60b91206a2e05a0c0e9e7a9892a319f66029bc2e659500cdc28b227021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67d62049976abf67d88182a6622399e82b505de6365a2c2d981ed420d980a4f5 0.600000000000 1641168 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": 1155561, "vin": [ { "gen": { "height": 1155551 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67d62049976abf67d88182a6622399e82b505de6365a2c2d981ed420d980a4f5" } } ], "extra": [ 1, 67, 98, 42, 9, 214, 11, 145, 32, 106, 46, 5, 160, 192, 233, 231, 169, 137, 42, 49, 159, 102, 2, 155, 194, 230, 89, 80, 12, 220, 40, 178, 39, 2, 17, 0, 0, 0, 1, 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