Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc50fa1145c372a2b44fa8975dcd1e393dce599bf11b5587f4af2cbb31379b99

Tx prefix hash: d812cdedfe2a2f0e14d702e8d14d38e257181b99f0f85aadf8da83245a255d00
Tx public key: c062d63dde83dd8193c0811a8020f3bed1d77019d10f736cec2e7b47fd7dbeb4
Timestamp: 1729993749 Timestamp [UCT]: 2024-10-27 01:49:09 Age [y:d:h:m:s]: 00:148:18:18:27
Block: 1140379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106098 RingCT/type: yes/0
Extra: 01c062d63dde83dd8193c0811a8020f3bed1d77019d10f736cec2e7b47fd7dbeb40211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00acde23dcaae3a4c34cb74dcf0823295983323e9a1e0b4b787b83c7c3b787af 0.600000000000 1624174 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": 1140389, "vin": [ { "gen": { "height": 1140379 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00acde23dcaae3a4c34cb74dcf0823295983323e9a1e0b4b787b83c7c3b787af" } } ], "extra": [ 1, 192, 98, 214, 61, 222, 131, 221, 129, 147, 192, 129, 26, 128, 32, 243, 190, 209, 215, 112, 25, 209, 15, 115, 108, 236, 46, 123, 71, 253, 125, 190, 180, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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