Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60eb8e1459708302a1da95e7846029d4bc704009be9c7a42244fc8c66bd29d88

Tx prefix hash: cc86168004e5c2e10d5d9961808376c7316ae31c197cd8aec9ba57c652e2fc8d
Tx public key: 891ab77d470dc9444e6421a62446dfb96e018c0d086376bc9c48b80125ef43b0
Timestamp: 1736714284 Timestamp [UCT]: 2025-01-12 20:38:04 Age [y:d:h:m:s]: 00:064:13:27:30
Block: 1195977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45931 RingCT/type: yes/0
Extra: 01891ab77d470dc9444e6421a62446dfb96e018c0d086376bc9c48b80125ef43b00211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40814c4ae8a577bdebfea0e16f232dddbedec0d11fbe7d1c896cfd4b1b601606 0.600000000000 1682574 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": 1195987, "vin": [ { "gen": { "height": 1195977 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40814c4ae8a577bdebfea0e16f232dddbedec0d11fbe7d1c896cfd4b1b601606" } } ], "extra": [ 1, 137, 26, 183, 125, 71, 13, 201, 68, 78, 100, 33, 166, 36, 70, 223, 185, 110, 1, 140, 13, 8, 99, 118, 188, 156, 72, 184, 1, 37, 239, 67, 176, 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