Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f58a2309ea52a57676468fb114394df20d7f28f8518618b11e6d2afa6ce2c9e7

Tx prefix hash: b54d71cd166f53df5225a020d221a82569be18dbdb4c909b9a2cd94246dc804c
Tx public key: 6b7d49884b9b3a3ae8f93cd5974ba865ce334a399979eb214d16d90b23e25aad
Timestamp: 1735590556 Timestamp [UCT]: 2024-12-30 20:29:16 Age [y:d:h:m:s]: 00:073:19:32:26
Block: 1186674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 52558 RingCT/type: yes/0
Extra: 016b7d49884b9b3a3ae8f93cd5974ba865ce334a399979eb214d16d90b23e25aad021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95c5cf894ed841dea505e6ee452b53d48f4a88426797cd83b066ab899bf3f86e 0.600000000000 1673159 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": 1186684, "vin": [ { "gen": { "height": 1186674 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95c5cf894ed841dea505e6ee452b53d48f4a88426797cd83b066ab899bf3f86e" } } ], "extra": [ 1, 107, 125, 73, 136, 75, 155, 58, 58, 232, 249, 60, 213, 151, 75, 168, 101, 206, 51, 74, 57, 153, 121, 235, 33, 77, 22, 217, 11, 35, 226, 90, 173, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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