Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4d4707c809026ceaf461209c1b7a27f961541bfc7e513b543f6f32ca9b7f720

Tx prefix hash: aadee6e4eda858839c800e363201c2a6acefa7d798e6c809cc269dc1ad3e58a2
Tx public key: ec7a1bc7ae2aa61b868d222cada6b68d813eed4f36f8087c813e881ebd5be632
Timestamp: 1647799337 Timestamp [UCT]: 2022-03-20 18:02:17 Age [y:d:h:m:s]: 03:203:07:55:42
Block: 462675 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 923173 RingCT/type: yes/0
Extra: 01ec7a1bc7ae2aa61b868d222cada6b68d813eed4f36f8087c813e881ebd5be63202110000000ed3fcec30000000000000000000

1 output(s) for total of 17.987297581000 dcy

stealth address amount amount idx
00: 5bdffb48ef3f952ef9459a79f4bdcc7ba320c216f951e06140727c60b6eca113 17.987297581000 880174 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": 462685, "vin": [ { "gen": { "height": 462675 } } ], "vout": [ { "amount": 17987297581, "target": { "key": "5bdffb48ef3f952ef9459a79f4bdcc7ba320c216f951e06140727c60b6eca113" } } ], "extra": [ 1, 236, 122, 27, 199, 174, 42, 166, 27, 134, 141, 34, 44, 173, 166, 182, 141, 129, 62, 237, 79, 54, 248, 8, 124, 129, 62, 136, 30, 189, 91, 230, 50, 2, 17, 0, 0, 0, 14, 211, 252, 236, 48, 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