Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50905bafe6efc60a516338ebae35e024c1e2c8832bfedbe7b1a4a24a4a778286

Tx prefix hash: af807abe4b7a63a5072387085ed3e27ead38c92342ed253e4b9480d65702b0db
Tx public key: f38a5b0206ea3da4efe79ae4942aa74d6bcf21ba9190c6a108221e38e1dcf476
Timestamp: 1736319544 Timestamp [UCT]: 2025-01-08 06:59:04 Age [y:d:h:m:s]: 00:109:01:44:49
Block: 1192709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77754 RingCT/type: yes/0
Extra: 01f38a5b0206ea3da4efe79ae4942aa74d6bcf21ba9190c6a108221e38e1dcf4760211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 408dff2a09eef2f2c64c58b84e0684876686889d166862a8e37193e4d79a0aa5 0.600000000000 1679264 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": 1192719, "vin": [ { "gen": { "height": 1192709 } } ], "vout": [ { "amount": 600000000, "target": { "key": "408dff2a09eef2f2c64c58b84e0684876686889d166862a8e37193e4d79a0aa5" } } ], "extra": [ 1, 243, 138, 91, 2, 6, 234, 61, 164, 239, 231, 154, 228, 148, 42, 167, 77, 107, 207, 33, 186, 145, 144, 198, 161, 8, 34, 30, 56, 225, 220, 244, 118, 2, 17, 0, 0, 0, 1, 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