Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 583ea50852a73a9e7ef0ae911dcd570c6fb36eb0975559ebc766dc082ed69213

Tx prefix hash: 26945218a1353a1266077f50a36172e969f00c952d8eed6266b86d31db478c21
Tx public key: 7b44a1d0cc4d88b846114c474aa8565edbe089e53db7e82feb714ff481bafba6
Timestamp: 1715930940 Timestamp [UCT]: 2024-05-17 07:29:00 Age [y:d:h:m:s]: 00:255:06:31:13
Block: 1023825 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182451 RingCT/type: yes/0
Extra: 017b44a1d0cc4d88b846114c474aa8565edbe089e53db7e82feb714ff481bafba602110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb6510e8018e6133b36ecb274d0ae19d0ef43f0fb8f67244527f66c3419da069 0.600000000000 1489092 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": 1023835, "vin": [ { "gen": { "height": 1023825 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb6510e8018e6133b36ecb274d0ae19d0ef43f0fb8f67244527f66c3419da069" } } ], "extra": [ 1, 123, 68, 161, 208, 204, 77, 136, 184, 70, 17, 76, 71, 74, 168, 86, 94, 219, 224, 137, 229, 61, 183, 232, 47, 235, 113, 79, 244, 129, 186, 251, 166, 2, 17, 0, 0, 0, 9, 82, 212, 126, 148, 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