Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3eb4d1326447b9d453ac2ca2aba55a2e0da2a6526cf2207f03c06be5cdfb4a8

Tx prefix hash: 896c41d68ce62104b4690c929d4d09a2a465409e13a7f60391a77cd921661b3b
Tx public key: 8e2074380016734ca9e6d44e30a44b68f77f951f22f16db69a69df548b30afbb
Timestamp: 1717567808 Timestamp [UCT]: 2024-06-05 06:10:08 Age [y:d:h:m:s]: 00:313:15:48:08
Block: 1037396 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224158 RingCT/type: yes/0
Extra: 018e2074380016734ca9e6d44e30a44b68f77f951f22f16db69a69df548b30afbb02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1050821c6a76de5dcef4f6696b30900c6a227faf86df2a329212cbf4c2bf7ffc 0.600000000000 1505927 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": 1037406, "vin": [ { "gen": { "height": 1037396 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1050821c6a76de5dcef4f6696b30900c6a227faf86df2a329212cbf4c2bf7ffc" } } ], "extra": [ 1, 142, 32, 116, 56, 0, 22, 115, 76, 169, 230, 212, 78, 48, 164, 75, 104, 247, 127, 149, 31, 34, 241, 109, 182, 154, 105, 223, 84, 139, 48, 175, 187, 2, 17, 0, 0, 0, 1, 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