Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c308239fa908bbe1f6d4181da840b5e8de92d0089fc25911f0928791aa2758bd

Tx prefix hash: 3828ee28d4a4ed209fcc4f06c61aecb797b2b318c78ca8f912781b86e5c25154
Tx public key: d506e469fc5de079b0ad302c9c0a2750ad85aeab1da87f75ba6b44b4a4d5f5a1
Timestamp: 1702706332 Timestamp [UCT]: 2023-12-16 05:58:52 Age [y:d:h:m:s]: 01:109:03:00:45
Block: 914177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339119 RingCT/type: yes/0
Extra: 01d506e469fc5de079b0ad302c9c0a2750ad85aeab1da87f75ba6b44b4a4d5f5a102110000000675e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b35f2f0957859442dcde61a5f4f8cc2eee36475ab9ab5bb59d42d146299e29b4 0.600000000000 1371463 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": 914187, "vin": [ { "gen": { "height": 914177 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b35f2f0957859442dcde61a5f4f8cc2eee36475ab9ab5bb59d42d146299e29b4" } } ], "extra": [ 1, 213, 6, 228, 105, 252, 93, 224, 121, 176, 173, 48, 44, 156, 10, 39, 80, 173, 133, 174, 171, 29, 168, 127, 117, 186, 107, 68, 180, 164, 213, 245, 161, 2, 17, 0, 0, 0, 6, 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