Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2023414de61db654338a95b1cabb529eb997606d33b062d814fd353f04bfb00a

Tx prefix hash: 8153d49e7dc1243788abab035338646fbd93ff23005a147feca7fd4f9c67affa
Tx public key: 6dab50f1a12ce5133d1760ae9e0b61639937c2000f4aa4d54542e7d70ee59d89
Timestamp: 1698352067 Timestamp [UCT]: 2023-10-26 20:27:47 Age [y:d:h:m:s]: 01:147:12:15:40
Block: 878300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366416 RingCT/type: yes/0
Extra: 016dab50f1a12ce5133d1760ae9e0b61639937c2000f4aa4d54542e7d70ee59d8902110000000275e3f0e9000000000000000000

1 output(s) for total of 0.754792395000 dcy

stealth address amount amount idx
00: 14f6f1cff98a5029aa67b6577e0c6c4da35a577827a697724573ecf75944c5d5 0.754792395000 1333730 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": 878310, "vin": [ { "gen": { "height": 878300 } } ], "vout": [ { "amount": 754792395, "target": { "key": "14f6f1cff98a5029aa67b6577e0c6c4da35a577827a697724573ecf75944c5d5" } } ], "extra": [ 1, 109, 171, 80, 241, 161, 44, 229, 19, 61, 23, 96, 174, 158, 11, 97, 99, 153, 55, 194, 0, 15, 74, 164, 213, 69, 66, 231, 215, 14, 229, 157, 137, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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