Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e276cd75b55f71fe5e6b09b1f4c50976278b5f7e64e90a7da49d61a367f7b620

Tx prefix hash: 2664787e7c6b3631fc4093bc25593f402f27ac374a6ea4e2e47919694acbe5e4
Tx public key: 31f4e03dfe974f1c8476f8cefc8706d81dab454e5533d89d6b72ef2056eb0b7d
Timestamp: 1736069918 Timestamp [UCT]: 2025-01-05 09:38:38 Age [y:d:h:m:s]: 00:103:20:49:58
Block: 1190660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74006 RingCT/type: yes/0
Extra: 0131f4e03dfe974f1c8476f8cefc8706d81dab454e5533d89d6b72ef2056eb0b7d0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a575b1b50baa068353601c4036b39bf1a38b0c116eace8063b97af9702e03a6b 0.600000000000 1677177 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": 1190670, "vin": [ { "gen": { "height": 1190660 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a575b1b50baa068353601c4036b39bf1a38b0c116eace8063b97af9702e03a6b" } } ], "extra": [ 1, 49, 244, 224, 61, 254, 151, 79, 28, 132, 118, 248, 206, 252, 135, 6, 216, 29, 171, 69, 78, 85, 51, 216, 157, 107, 114, 239, 32, 86, 235, 11, 125, 2, 17, 0, 0, 0, 2, 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