Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed5594ce591cb2225212e477d300303e7b47a3f60c4fa1f618588835c2783477

Tx prefix hash: f8210d8b7a7315be4f257b848d8129263522d644daa21a998462ea019e14f2d5
Tx public key: 9905cd8d8e42fba19c1b521cc2178a5b99228e2af2ad91a5ddc505d32070e9a1
Timestamp: 1702669392 Timestamp [UCT]: 2023-12-15 19:43:12 Age [y:d:h:m:s]: 01:183:23:38:30
Block: 913872 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 392572 RingCT/type: yes/0
Extra: 019905cd8d8e42fba19c1b521cc2178a5b99228e2af2ad91a5ddc505d32070e9a102110000000333af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b56a2758b93fcaf9952eec4662cd9c6a7e13103c8a93d574e5e63eff8f26d52f 0.600000000000 1371152 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": 913882, "vin": [ { "gen": { "height": 913872 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b56a2758b93fcaf9952eec4662cd9c6a7e13103c8a93d574e5e63eff8f26d52f" } } ], "extra": [ 1, 153, 5, 205, 141, 142, 66, 251, 161, 156, 27, 82, 28, 194, 23, 138, 91, 153, 34, 142, 42, 242, 173, 145, 165, 221, 197, 5, 211, 32, 112, 233, 161, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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