Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7fb669d18dd397513cc26b3ef05369161f31d66ee29e0dfe71886a1d0858391c

Tx prefix hash: 106c9b8d4d03d4d4549dff511329844c6c54b0e52622d2a2e3a93ca4dfd53eb6
Tx public key: 057f72266e68f174f5a7e4f525e115685943f8c5302c52bcaff77647dfd1a38b
Timestamp: 1715511441 Timestamp [UCT]: 2024-05-12 10:57:21 Age [y:d:h:m:s]: 01:016:17:17:53
Block: 1020378 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272856 RingCT/type: yes/0
Extra: 01057f72266e68f174f5a7e4f525e115685943f8c5302c52bcaff77647dfd1a38b021100000003679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2bfe00cbda6376b5bc04c5140a2db91378bd976cf5fa05f8f566a377add2e753 0.600000000000 1484443 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": 1020388, "vin": [ { "gen": { "height": 1020378 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2bfe00cbda6376b5bc04c5140a2db91378bd976cf5fa05f8f566a377add2e753" } } ], "extra": [ 1, 5, 127, 114, 38, 110, 104, 241, 116, 245, 167, 228, 245, 37, 225, 21, 104, 89, 67, 248, 197, 48, 44, 82, 188, 175, 247, 118, 71, 223, 209, 163, 139, 2, 17, 0, 0, 0, 3, 103, 154, 138, 129, 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