Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 135408eea1f9a90339784cc709876443f69458f38ce90ebb74b6f371b8aa2acf

Tx prefix hash: 24fc0f6f0334e65352db83e9b896dc1acaa7309c7fb509e27ffedce974c9b471
Tx public key: d16a1ba44617d933f60a69ddf53900ee88e6e3bcd6a370aaac8daa6c0252c0f7
Timestamp: 1703908672 Timestamp [UCT]: 2023-12-30 03:57:52 Age [y:d:h:m:s]: 01:130:00:14:46
Block: 924145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354049 RingCT/type: yes/0
Extra: 01d16a1ba44617d933f60a69ddf53900ee88e6e3bcd6a370aaac8daa6c0252c0f7021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 22e8310f89bcf119b5863df8e58e27c3838e03d8636944a0eaef9e8bedea9787 0.600000000000 1381889 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": 924155, "vin": [ { "gen": { "height": 924145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "22e8310f89bcf119b5863df8e58e27c3838e03d8636944a0eaef9e8bedea9787" } } ], "extra": [ 1, 209, 106, 27, 164, 70, 23, 217, 51, 246, 10, 105, 221, 245, 57, 0, 238, 136, 230, 227, 188, 214, 163, 112, 170, 172, 141, 170, 108, 2, 82, 192, 247, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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