Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b02ca5db10521410fa372c003ae1e45dc7cb93e71b7a9c3c0b7941fc688f5a2d

Tx prefix hash: 0895ec814a146a4e26ea69403e46e8f5c9378f4233e35cc0f95b52595ad6cbd5
Tx public key: 8280790b0f26dd023d6d2a0e00f23bbff94309e0115cf3dd6f0c7bc8eaec2826
Timestamp: 1715158748 Timestamp [UCT]: 2024-05-08 08:59:08 Age [y:d:h:m:s]: 00:265:14:52:15
Block: 1017429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189838 RingCT/type: yes/0
Extra: 018280790b0f26dd023d6d2a0e00f23bbff94309e0115cf3dd6f0c7bc8eaec28260211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fac65b237d1e258869cc1c5acb6c876fdf9817be599a2ac01cb3774321b5e6df 0.600000000000 1481212 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": 1017439, "vin": [ { "gen": { "height": 1017429 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fac65b237d1e258869cc1c5acb6c876fdf9817be599a2ac01cb3774321b5e6df" } } ], "extra": [ 1, 130, 128, 121, 11, 15, 38, 221, 2, 61, 109, 42, 14, 0, 242, 59, 191, 249, 67, 9, 224, 17, 92, 243, 221, 111, 12, 123, 200, 234, 236, 40, 38, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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