Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2bef8140118d2abd4e08c6644c006a13b0674d642922b3e97ae6f2912f3ee2dc

Tx prefix hash: 1272a01da4da7b3c9a75f37a00f17062de8d6fb90abb5a94e1f55bfb89caae69
Tx public key: 34ff2b95ef6568efdfb3fd5e3bf5422f73b62756a394604c7a8cc3630314a433
Timestamp: 1720425025 Timestamp [UCT]: 2024-07-08 07:50:25 Age [y:d:h:m:s]: 00:309:20:52:15
Block: 1061085 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221425 RingCT/type: yes/0
Extra: 0134ff2b95ef6568efdfb3fd5e3bf5422f73b62756a394604c7a8cc3630314a433021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3fe44a3f90daf50ee0bccd4240275211187750efdcb82c1b4293c1e3af1820ee 0.600000000000 1531576 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": 1061095, "vin": [ { "gen": { "height": 1061085 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3fe44a3f90daf50ee0bccd4240275211187750efdcb82c1b4293c1e3af1820ee" } } ], "extra": [ 1, 52, 255, 43, 149, 239, 101, 104, 239, 223, 179, 253, 94, 59, 245, 66, 47, 115, 182, 39, 86, 163, 148, 96, 76, 122, 140, 195, 99, 3, 20, 164, 51, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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