Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fceaeca4d7d3c632ff4713f65cbb8abe2f3ae88bf86d70f76208cad585468fc5

Tx prefix hash: f10d7e370b15d7b9f5901ea3f8b769654a7442c4dacb5a4c1ea6f0f4c4911aeb
Tx public key: ba8610768f616f3ec0ee0994513de2bd404dd25d8882bc8aab727dfafca2608c
Timestamp: 1711635823 Timestamp [UCT]: 2024-03-28 14:23:43 Age [y:d:h:m:s]: 01:048:04:16:58
Block: 988235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295398 RingCT/type: yes/0
Extra: 01ba8610768f616f3ec0ee0994513de2bd404dd25d8882bc8aab727dfafca2608c02110000000c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fe44d83a74cab17a1ec7f792a1419a4d8a5b6b370692335e2447fe25d1a4e6a 0.600000000000 1448508 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": 988245, "vin": [ { "gen": { "height": 988235 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fe44d83a74cab17a1ec7f792a1419a4d8a5b6b370692335e2447fe25d1a4e6a" } } ], "extra": [ 1, 186, 134, 16, 118, 143, 97, 111, 62, 192, 238, 9, 148, 81, 61, 226, 189, 64, 77, 210, 93, 136, 130, 188, 138, 171, 114, 125, 250, 252, 162, 96, 140, 2, 17, 0, 0, 0, 12, 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