Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f28cd0db91aad8a739d5bf522e7367f2be6ccfc1fbf1dea364c9e9f66b67ecf0

Tx prefix hash: c84b38a5d01feb64868fea2aaa2ea404139eab89495296f8b34e75d86d11fd83
Tx public key: 1047b10b43b2894e3bc4d4c3e7284c19c6261b59bc60e00aa9d6b1486508a133
Timestamp: 1701198781 Timestamp [UCT]: 2023-11-28 19:13:01 Age [y:d:h:m:s]: 02:032:08:10:39
Block: 901687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 542919 RingCT/type: yes/0
Extra: 011047b10b43b2894e3bc4d4c3e7284c19c6261b59bc60e00aa9d6b1486508a133021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.631446618000 dcy

stealth address amount amount idx
00: cb4c4b58c9d4d7cc554e1db907b1c4e89020113b191264b5bb39113ebf4219d6 0.631446618000 1358270 of 0

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": 901697, "vin": [ { "gen": { "height": 901687 } } ], "vout": [ { "amount": 631446618, "target": { "key": "cb4c4b58c9d4d7cc554e1db907b1c4e89020113b191264b5bb39113ebf4219d6" } } ], "extra": [ 1, 16, 71, 177, 11, 67, 178, 137, 78, 59, 196, 212, 195, 231, 40, 76, 25, 198, 38, 27, 89, 188, 96, 224, 10, 169, 214, 177, 72, 101, 8, 161, 51, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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