Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5bd77bcf0811b628ad69e33652aea7730dbfae6a26f30cab578f661e5cc69c31

Tx prefix hash: 3b6d1a4092a43d7ae5c059752329d347516f4ab4d4f801c3a195c8220f792623
Tx public key: e979f46ef50634d45b8b11a729ef2cfb371058c53c2cdd7fabeb51109f99b262
Timestamp: 1725622304 Timestamp [UCT]: 2024-09-06 11:31:44 Age [y:d:h:m:s]: 00:107:17:08:32
Block: 1104170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77063 RingCT/type: yes/0
Extra: 01e979f46ef50634d45b8b11a729ef2cfb371058c53c2cdd7fabeb51109f99b26202110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3161957292e9f79e48ec831d1319910b0f0c33eadac8362f2cbc278bd4d3653e 0.600000000000 1581249 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": 1104180, "vin": [ { "gen": { "height": 1104170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3161957292e9f79e48ec831d1319910b0f0c33eadac8362f2cbc278bd4d3653e" } } ], "extra": [ 1, 233, 121, 244, 110, 245, 6, 52, 212, 91, 139, 17, 167, 41, 239, 44, 251, 55, 16, 88, 197, 60, 44, 221, 127, 171, 235, 81, 16, 159, 153, 178, 98, 2, 17, 0, 0, 0, 3, 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