Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5ca161292bf1cd8b16194ef9e671c610f362b59990eeb28630165c70e6d8be8

Tx prefix hash: 96f155327004b754c31dd32be4f295063859124175e3b891b54ef9b0621acc38
Tx public key: 31db4f24d3905210a551e32f1afe80b529de44b0b9ccb4aeeffa3c8a3d87fcc3
Timestamp: 1736065345 Timestamp [UCT]: 2025-01-05 08:22:25 Age [y:d:h:m:s]: 00:165:11:11:52
Block: 1190619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117955 RingCT/type: yes/0
Extra: 0131db4f24d3905210a551e32f1afe80b529de44b0b9ccb4aeeffa3c8a3d87fcc302110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42cb8fd0500e3af1ee0299f2853a388f1e8c5b49896b30d832228123d3a99f0a 0.600000000000 1677136 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": 1190629, "vin": [ { "gen": { "height": 1190619 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42cb8fd0500e3af1ee0299f2853a388f1e8c5b49896b30d832228123d3a99f0a" } } ], "extra": [ 1, 49, 219, 79, 36, 211, 144, 82, 16, 165, 81, 227, 47, 26, 254, 128, 181, 41, 222, 68, 176, 185, 204, 180, 174, 239, 250, 60, 138, 61, 135, 252, 195, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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