Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 856f48d3d9ab3f8c3eddaba9724f1c18015dad56df7c3642d0385236ba30a0d5

Tx prefix hash: 43bb5df03ffd69d79c7b6fa13d50bdb7f30dd2fce52cda87903796e77f79ba29
Tx public key: 94105ebad83aea2a32f1e2008ca0a522b74e45c629c71af9dd2aeb780d905453
Timestamp: 1682204777 Timestamp [UCT]: 2023-04-22 23:06:17 Age [y:d:h:m:s]: 02:196:08:09:45
Block: 744467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 660164 RingCT/type: yes/0
Extra: 0194105ebad83aea2a32f1e2008ca0a522b74e45c629c71af9dd2aeb780d905453021100000005faf35c9c000000000000000000

1 output(s) for total of 2.095424403000 dcy

stealth address amount amount idx
00: 1f964196857a030b17012368ed56191bd82e9eec79b619a89a4eddc558f1aa27 2.095424403000 1191790 of 0

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": 744477, "vin": [ { "gen": { "height": 744467 } } ], "vout": [ { "amount": 2095424403, "target": { "key": "1f964196857a030b17012368ed56191bd82e9eec79b619a89a4eddc558f1aa27" } } ], "extra": [ 1, 148, 16, 94, 186, 216, 58, 234, 42, 50, 241, 226, 0, 140, 160, 165, 34, 183, 78, 69, 198, 41, 199, 26, 249, 221, 42, 235, 120, 13, 144, 84, 83, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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