Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30f89ad4fc696a17c851669a2267bf977b81ef341854b853c5c20163632be44d

Tx prefix hash: 8a758b727062e5bfcb3c9106d5494db013636a98b71b1199568fa8e4bbf53299
Tx public key: 85dea7969b0fcf2ff0d5301d2e182a53f73ddbaa90a6c318ab9c236f9d576f23
Timestamp: 1736849249 Timestamp [UCT]: 2025-01-14 10:07:29 Age [y:d:h:m:s]: 00:304:01:44:56
Block: 1197103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214823 RingCT/type: yes/0
Extra: 0185dea7969b0fcf2ff0d5301d2e182a53f73ddbaa90a6c318ab9c236f9d576f230211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb32f1083ddd5fe00385d1305c5884b381a00c1af6dabd5955a64eaa554e4128 0.600000000000 1683708 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": 1197113, "vin": [ { "gen": { "height": 1197103 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb32f1083ddd5fe00385d1305c5884b381a00c1af6dabd5955a64eaa554e4128" } } ], "extra": [ 1, 133, 222, 167, 150, 155, 15, 207, 47, 240, 213, 48, 29, 46, 24, 42, 83, 247, 61, 219, 170, 144, 166, 195, 24, 171, 156, 35, 111, 157, 87, 111, 35, 2, 17, 0, 0, 0, 7, 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