Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0202dd35ca6c56b86efc48f8b9f023f16d465b91a317029fcec53e0dff0bfcf5

Tx prefix hash: e2845258b90e50d98935faeb38c06fdb5f14e69d4cd324fb024b92924c9c442a
Tx public key: ffadaffed0cefd7db63039f42c2df4e40a0d5c447d705934680597dcf0802cec
Timestamp: 1711563898 Timestamp [UCT]: 2024-03-27 18:24:58 Age [y:d:h:m:s]: 01:236:21:45:37
Block: 987632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 428000 RingCT/type: yes/0
Extra: 01ffadaffed0cefd7db63039f42c2df4e40a0d5c447d705934680597dcf0802cec02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e544997a8282ec49be171db77331b9a2e370aff2ec1a28fdc5b1935e1c11ef17 0.600000000000 1447885 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": 987642, "vin": [ { "gen": { "height": 987632 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e544997a8282ec49be171db77331b9a2e370aff2ec1a28fdc5b1935e1c11ef17" } } ], "extra": [ 1, 255, 173, 175, 254, 208, 206, 253, 125, 182, 48, 57, 244, 44, 45, 244, 228, 10, 13, 92, 68, 125, 112, 89, 52, 104, 5, 151, 220, 240, 128, 44, 236, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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