Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd452367e8945a4897ed61f18b6e0b07dbc96211a307c4cd750bb53c170bec91

Tx prefix hash: 494f90c407cf44ceadf4220f052b043181784e57396a7b4dd7fd48a004bf05f7
Tx public key: 9f393c09e1bb105f75b98410f50d4f5b178cf2af81e986af9a008140f9abfb8d
Timestamp: 1697259759 Timestamp [UCT]: 2023-10-14 05:02:39 Age [y:d:h:m:s]: 01:179:17:47:14
Block: 869232 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389486 RingCT/type: yes/0
Extra: 019f393c09e1bb105f75b98410f50d4f5b178cf2af81e986af9a008140f9abfb8d02110000000533af99f4000000000000000000

1 output(s) for total of 0.808860406000 dcy

stealth address amount amount idx
00: ea4dba1725aa888f58126c395ca055ef3b44186212c1a0dcd4acf8eca17162b2 0.808860406000 1324071 of 0

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": 869242, "vin": [ { "gen": { "height": 869232 } } ], "vout": [ { "amount": 808860406, "target": { "key": "ea4dba1725aa888f58126c395ca055ef3b44186212c1a0dcd4acf8eca17162b2" } } ], "extra": [ 1, 159, 57, 60, 9, 225, 187, 16, 95, 117, 185, 132, 16, 245, 13, 79, 91, 23, 140, 242, 175, 129, 233, 134, 175, 154, 0, 129, 64, 249, 171, 251, 141, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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