Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aabc5010aacc163ded1c5334b9976b4f9bb83a2edf579b783a735576e2f73ea6

Tx prefix hash: 33c8dfbeba8c0c8966c8526ef71310eb4ff00f4ce793f3053ed657f2fda174ba
Tx public key: bfb6bacfd629af64a2d3a4ab51fb5bc3d7069aabbd47f3b60ea535a34f3cd52a
Timestamp: 1707711469 Timestamp [UCT]: 2024-02-12 04:17:49 Age [y:d:h:m:s]: 00:315:02:23:11
Block: 955668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225629 RingCT/type: yes/0
Extra: 01bfb6bacfd629af64a2d3a4ab51fb5bc3d7069aabbd47f3b60ea535a34f3cd52a02110000001059dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8a1d9859d2929d5b2037d3da9add2e872a8b6162f9365f8012e5073e355d6e0 0.600000000000 1414966 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": 955678, "vin": [ { "gen": { "height": 955668 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8a1d9859d2929d5b2037d3da9add2e872a8b6162f9365f8012e5073e355d6e0" } } ], "extra": [ 1, 191, 182, 186, 207, 214, 41, 175, 100, 162, 211, 164, 171, 81, 251, 91, 195, 215, 6, 154, 171, 189, 71, 243, 182, 14, 165, 53, 163, 79, 60, 213, 42, 2, 17, 0, 0, 0, 16, 89, 218, 211, 245, 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