Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1dcc6b10a58bb08ec96e59a21cbbed807662a9b88134237ff368f31c3546b40c

Tx prefix hash: 454f0e07ed19377a8b4619136d12e059922cb35e2aa44981e293134f9bfa29af
Tx public key: bda4fc2dd6c1d2d9a9d61db8cbf1a1959663056a886a32c5cfc5a4576ad84cbd
Timestamp: 1705302462 Timestamp [UCT]: 2024-01-15 07:07:42 Age [y:d:h:m:s]: 00:275:16:21:36
Block: 935684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197494 RingCT/type: yes/0
Extra: 01bda4fc2dd6c1d2d9a9d61db8cbf1a1959663056a886a32c5cfc5a4576ad84cbd02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84c6cca1d6cf4437f41c1ab857a3c87861081346df43bb8c04402236583572ea 0.600000000000 1393700 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": 935694, "vin": [ { "gen": { "height": 935684 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84c6cca1d6cf4437f41c1ab857a3c87861081346df43bb8c04402236583572ea" } } ], "extra": [ 1, 189, 164, 252, 45, 214, 193, 210, 217, 169, 214, 29, 184, 203, 241, 161, 149, 150, 99, 5, 106, 136, 106, 50, 197, 207, 197, 164, 87, 106, 216, 76, 189, 2, 17, 0, 0, 0, 3, 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