Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f13de4d8a9809cca1e572f8e64dbe5cf16402840d36ef1a8e5ca713cece1a15e

Tx prefix hash: 7a1e93d5ea18daadaaab1d0afc1e8ad99556fd9386c5676b040cb13a9a3d6fe9
Tx public key: d58ccda27d78190ffe5d4f6a04161e361a96c60e44c9f5eff7710c3f25cb6b57
Timestamp: 1710138387 Timestamp [UCT]: 2024-03-11 06:26:27 Age [y:d:h:m:s]: 01:033:17:39:33
Block: 975809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285113 RingCT/type: yes/0
Extra: 01d58ccda27d78190ffe5d4f6a04161e361a96c60e44c9f5eff7710c3f25cb6b570211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06e2320ad3522a9f71008ff4096185a64240583bb2b0739cdd75ea3365c784d2 0.600000000000 1435784 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": 975819, "vin": [ { "gen": { "height": 975809 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06e2320ad3522a9f71008ff4096185a64240583bb2b0739cdd75ea3365c784d2" } } ], "extra": [ 1, 213, 140, 205, 162, 125, 120, 25, 15, 254, 93, 79, 106, 4, 22, 30, 54, 26, 150, 198, 14, 68, 201, 245, 239, 247, 113, 12, 63, 37, 203, 107, 87, 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