Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5274b2a9830ed05c81958d4d7eaf94eb4adc574cd16852811c331470d251a13

Tx prefix hash: fdb70d73a152607e441f1a66e3593ba42b579a24677846e99388db07d113c4f2
Tx public key: 8d392f657d11a408160730dc9105c1217ba041f1708c69e20287d116f8a7f0cc
Timestamp: 1697337957 Timestamp [UCT]: 2023-10-15 02:45:57 Age [y:d:h:m:s]: 01:220:11:56:51
Block: 869878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 418660 RingCT/type: yes/0
Extra: 018d392f657d11a408160730dc9105c1217ba041f1708c69e20287d116f8a7f0cc02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.804883658000 dcy

stealth address amount amount idx
00: 4c1e7cc561dd38d0fe6776be68a45df3fe2f81720f1aa5b0c054e8fa536a0fa6 0.804883658000 1324743 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": 869888, "vin": [ { "gen": { "height": 869878 } } ], "vout": [ { "amount": 804883658, "target": { "key": "4c1e7cc561dd38d0fe6776be68a45df3fe2f81720f1aa5b0c054e8fa536a0fa6" } } ], "extra": [ 1, 141, 57, 47, 101, 125, 17, 164, 8, 22, 7, 48, 220, 145, 5, 193, 33, 123, 160, 65, 241, 112, 140, 105, 226, 2, 135, 209, 22, 248, 167, 240, 204, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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