Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ed4e19484b3efa331a76b4c113c1426be72fdbce0d4f64b068ea578c38aaf5f

Tx prefix hash: dcca05143161424a59f5418dcad094d93b98eb72d7c423abdbb8b710d75460d4
Tx public key: 7c71a4589d0cce2d78a12f7237a2018161cc0c029f93a96c13a7ad6d93e0cf04
Timestamp: 1730280965 Timestamp [UCT]: 2024-10-30 09:36:05 Age [y:d:h:m:s]: 00:150:20:40:53
Block: 1142717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107645 RingCT/type: yes/0
Extra: 017c71a4589d0cce2d78a12f7237a2018161cc0c029f93a96c13a7ad6d93e0cf04021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be0df2f2711cc35543e6a94ecbe858c285751e407b96514d86462e33ee03dfd5 0.600000000000 1626572 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": 1142727, "vin": [ { "gen": { "height": 1142717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be0df2f2711cc35543e6a94ecbe858c285751e407b96514d86462e33ee03dfd5" } } ], "extra": [ 1, 124, 113, 164, 88, 157, 12, 206, 45, 120, 161, 47, 114, 55, 162, 1, 129, 97, 204, 12, 2, 159, 147, 169, 108, 19, 167, 173, 109, 147, 224, 207, 4, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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