Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 377f376c8c43700f7e5129145f84b00b52a2bc71b381f8ea47163c3013584463

Tx prefix hash: 8034ca62dc19c7bb27abd20c4f2ffa8adbda54fabdc49253dc388cab8c5d1bc7
Tx public key: 3527d9ae685d8fb2a2f782afc499c48618b634e476a353f14af8df20f2e35768
Timestamp: 1730710600 Timestamp [UCT]: 2024-11-04 08:56:40 Age [y:d:h:m:s]: 01:006:16:11:42
Block: 1146254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263197 RingCT/type: yes/0
Extra: 013527d9ae685d8fb2a2f782afc499c48618b634e476a353f14af8df20f2e357680211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abe4031bc986cf808671ff3cd8a40248bc28b692d3dcf6230a71dda499b96ec6 0.600000000000 1630861 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": 1146264, "vin": [ { "gen": { "height": 1146254 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abe4031bc986cf808671ff3cd8a40248bc28b692d3dcf6230a71dda499b96ec6" } } ], "extra": [ 1, 53, 39, 217, 174, 104, 93, 143, 178, 162, 247, 130, 175, 196, 153, 196, 134, 24, 182, 52, 228, 118, 163, 83, 241, 74, 248, 223, 32, 242, 227, 87, 104, 2, 17, 0, 0, 0, 3, 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