Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6b1a01b0fb1fc6ec295f0cf04f0d48ce5f9f0f073176330c098fa025e1c92e8

Tx prefix hash: f5328878f15c1343c6f4dbb5a382619316520d4d790fdbdf1838cb652d6eb721
Tx public key: 86ae27e84401e46c2885243be81475f9c69af525a6d16ec4c4a5fee4a94a46aa
Timestamp: 1741735645 Timestamp [UCT]: 2025-03-11 23:27:25 Age [y:d:h:m:s]: 00:298:16:33:41
Block: 1237294 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211287 RingCT/type: yes/0
Extra: 0186ae27e84401e46c2885243be81475f9c69af525a6d16ec4c4a5fee4a94a46aa02110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c53b9d6c0afb2a075aa5bb96ef617d08e20922ff2fb655af30ca13c200a666f 0.600000000000 1724249 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": 1237304, "vin": [ { "gen": { "height": 1237294 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c53b9d6c0afb2a075aa5bb96ef617d08e20922ff2fb655af30ca13c200a666f" } } ], "extra": [ 1, 134, 174, 39, 232, 68, 1, 228, 108, 40, 133, 36, 59, 232, 20, 117, 249, 198, 154, 245, 37, 166, 209, 110, 196, 196, 165, 254, 228, 169, 74, 70, 170, 2, 17, 0, 0, 0, 11, 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