Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d568bc3557a1465f532bd9ca7fec6ed3dd3df680315b256ee783e2e187445c9

Tx prefix hash: cedfff5a7ca6d0eb0ea9903f704d99ca2d8708ba7295c4a4e631c476d93b81f9
Tx public key: afd1537925239bce41b4bb6d9b305db704ac6ad3a02bd5693cd8314c27d9af7d
Timestamp: 1734679948 Timestamp [UCT]: 2024-12-20 07:32:28 Age [y:d:h:m:s]: 00:094:12:52:43
Block: 1179168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67317 RingCT/type: yes/0
Extra: 01afd1537925239bce41b4bb6d9b305db704ac6ad3a02bd5693cd8314c27d9af7d0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: acfb582a120b78ac3ac9e8d1e358a3897eb586344bf3f328f8e1d8c8dc220285 0.600000000000 1665559 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": 1179178, "vin": [ { "gen": { "height": 1179168 } } ], "vout": [ { "amount": 600000000, "target": { "key": "acfb582a120b78ac3ac9e8d1e358a3897eb586344bf3f328f8e1d8c8dc220285" } } ], "extra": [ 1, 175, 209, 83, 121, 37, 35, 155, 206, 65, 180, 187, 109, 155, 48, 93, 183, 4, 172, 106, 211, 160, 43, 213, 105, 60, 216, 49, 76, 39, 217, 175, 125, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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