Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98fa674ba2ea3409b7845b62f578e33137076ee5dc22f9062166db70345db22c

Tx prefix hash: 549a4bebcc4c2d69309aad8b139c6231bbae6afc147e79a5305ee06d1aea064b
Tx public key: 6d9e489c8bd50d4a5b72f2e0d87616ea623bb5a4a5951315b77b78834f471b0b
Timestamp: 1717666770 Timestamp [UCT]: 2024-06-06 09:39:30 Age [y:d:h:m:s]: 01:128:09:35:13
Block: 1038219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0811 kB
Tx version: 2 No of confirmations: 350294 RingCT/type: yes/0
Extra: 016d9e489c8bd50d4a5b72f2e0d87616ea623bb5a4a5951315b77b78834f471b0b

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ca83589f68ad49f7584f9899e7c7871fb56cbea3edf58a8b3d9efb10bc3c10c 0.600000000000 1506780 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": 1038229, "vin": [ { "gen": { "height": 1038219 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ca83589f68ad49f7584f9899e7c7871fb56cbea3edf58a8b3d9efb10bc3c10c" } } ], "extra": [ 1, 109, 158, 72, 156, 139, 213, 13, 74, 91, 114, 242, 224, 216, 118, 22, 234, 98, 59, 181, 164, 165, 149, 19, 21, 183, 123, 120, 131, 79, 71, 27, 11 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8