Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75ef0c5410fe3cf2d8939ec89733751eafbe5dc28d0f4ff0df2234e031d92668

Tx prefix hash: 42790f0bb132ce43a47ebecb30c86093dd42966b848f236296ee0ba164fab563
Tx public key: 80d05bd0f1fe2e8392caf706e0353225b66f528e7b3e36cc49cbd0dd7d0811db
Timestamp: 1736668318 Timestamp [UCT]: 2025-01-12 07:51:58 Age [y:d:h:m:s]: 00:157:15:59:15
Block: 1195598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112378 RingCT/type: yes/0
Extra: 0180d05bd0f1fe2e8392caf706e0353225b66f528e7b3e36cc49cbd0dd7d0811db0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46fcc5d1ede470e86c6f5df8247ff8c20f384ab4bd1dc5f938b0ac2c7755103e 0.600000000000 1682189 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": 1195608, "vin": [ { "gen": { "height": 1195598 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46fcc5d1ede470e86c6f5df8247ff8c20f384ab4bd1dc5f938b0ac2c7755103e" } } ], "extra": [ 1, 128, 208, 91, 208, 241, 254, 46, 131, 146, 202, 247, 6, 224, 53, 50, 37, 182, 111, 82, 142, 123, 62, 54, 204, 73, 203, 208, 221, 125, 8, 17, 219, 2, 17, 0, 0, 0, 5, 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