Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdf7c38d994116df4fe1773c68e169fc5e1684416f822d7ba02d2e4c53c23805

Tx prefix hash: 3d473793c6872a53db37316c870e59b5230388631ac7a75551d4eeb25e0f7586
Tx public key: ba4c4b326ed4719dcace5f85c0b7ff5dfeea3e709b6ad0fcafb479f9e867768c
Timestamp: 1737344648 Timestamp [UCT]: 2025-01-20 03:44:08 Age [y:d:h:m:s]: 00:149:22:28:13
Block: 1201158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106881 RingCT/type: yes/0
Extra: 01ba4c4b326ed4719dcace5f85c0b7ff5dfeea3e709b6ad0fcafb479f9e867768c0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bdd3774071060485a4881f0f70a46868aae9cba247e0d4645a1e96707e04ff72 0.600000000000 1687807 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": 1201168, "vin": [ { "gen": { "height": 1201158 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdd3774071060485a4881f0f70a46868aae9cba247e0d4645a1e96707e04ff72" } } ], "extra": [ 1, 186, 76, 75, 50, 110, 212, 113, 157, 202, 206, 95, 133, 192, 183, 255, 93, 254, 234, 62, 112, 155, 106, 208, 252, 175, 180, 121, 249, 232, 103, 118, 140, 2, 17, 0, 0, 0, 4, 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