Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37b6ff00c19498266bad38589736326c3a1ee1e7a148f0f5a741bf1e35e717b5

Tx prefix hash: 865a0327e442a3238b9613e765be186ef9648a9a6e2ed16c649d3c8c1c1bc001
Tx public key: 79fb4ff1cdb92f6f9f3e38778e195a6b1f45475ad90786e4ee2f1462452a449a
Timestamp: 1715161925 Timestamp [UCT]: 2024-05-08 09:52:05 Age [y:d:h:m:s]: 01:229:10:23:11
Block: 1017456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 422640 RingCT/type: yes/0
Extra: 0179fb4ff1cdb92f6f9f3e38778e195a6b1f45475ad90786e4ee2f1462452a449a0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 462c12f722dca7fc1e9f05976d4aa33d91719946ced8eca643462814a77a77a4 0.600000000000 1481239 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": 1017466, "vin": [ { "gen": { "height": 1017456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "462c12f722dca7fc1e9f05976d4aa33d91719946ced8eca643462814a77a77a4" } } ], "extra": [ 1, 121, 251, 79, 241, 205, 185, 47, 111, 159, 62, 56, 119, 142, 25, 90, 107, 31, 69, 71, 90, 217, 7, 134, 228, 238, 47, 20, 98, 69, 42, 68, 154, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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