Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b28dabd4d586e00f919e7b639285ca49665be3386ea60328eb6533f5c1abf687

Tx prefix hash: 097e6e1f1b83c44c9d5c8ddb8b954c6920b69893216513b52af8cf778950ebed
Tx public key: d88e939f7777b4c4c961f31057395d92e9781058db4c4afc38a4432aa5095752
Timestamp: 1702088444 Timestamp [UCT]: 2023-12-09 02:20:44 Age [y:d:h:m:s]: 01:190:14:40:52
Block: 909051 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397329 RingCT/type: yes/0
Extra: 01d88e939f7777b4c4c961f31057395d92e9781058db4c4afc38a4432aa5095752021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27bf320a51f252b35eb4e54df64fa0567b65e89d9fcb48bdad296081ec7da0f7 0.600000000000 1366116 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": 909061, "vin": [ { "gen": { "height": 909051 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27bf320a51f252b35eb4e54df64fa0567b65e89d9fcb48bdad296081ec7da0f7" } } ], "extra": [ 1, 216, 142, 147, 159, 119, 119, 180, 196, 201, 97, 243, 16, 87, 57, 93, 146, 233, 120, 16, 88, 219, 76, 74, 252, 56, 164, 67, 42, 165, 9, 87, 82, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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