Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db3da0313763a087188a5fabb70d38ed3c1d6616f3c3c37253591c4bac4e0674

Tx prefix hash: 2bbf344491b456c9b94ac950acbeaf379a54e36d251b5891ebc2b91dde9c6760
Tx public key: cf91d7431e62f0b70b079c5c0fe531c8affe40fc6ad6af0c10f0b9113d93cab1
Timestamp: 1720910503 Timestamp [UCT]: 2024-07-13 22:41:43 Age [y:d:h:m:s]: 00:338:21:13:18
Block: 1065112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242050 RingCT/type: yes/0
Extra: 01cf91d7431e62f0b70b079c5c0fe531c8affe40fc6ad6af0c10f0b9113d93cab102110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b165338a179e06a8dec569e201e56a07f7f07c420ec215309136c335f5a976f 0.600000000000 1535655 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": 1065122, "vin": [ { "gen": { "height": 1065112 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b165338a179e06a8dec569e201e56a07f7f07c420ec215309136c335f5a976f" } } ], "extra": [ 1, 207, 145, 215, 67, 30, 98, 240, 183, 11, 7, 156, 92, 15, 229, 49, 200, 175, 254, 64, 252, 106, 214, 175, 12, 16, 240, 185, 17, 61, 147, 202, 177, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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