Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7606f9fe2990a695e3e3e1324b40bcdc6b8322c907215258b03eb3868d028ad7

Tx prefix hash: 495c122724e2b497c8f32d88f92e90c4ed0eacaa1f511d6386a89e33b40e4632
Tx public key: 828690d21a932f2c69d18dfa55bab3571bdaea04bebaceb09015d9a5cb769b93
Timestamp: 1729668798 Timestamp [UCT]: 2024-10-23 07:33:18 Age [y:d:h:m:s]: 00:183:21:18:46
Block: 1137681 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131238 RingCT/type: yes/0
Extra: 01828690d21a932f2c69d18dfa55bab3571bdaea04bebaceb09015d9a5cb769b93021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e65bcbfdd03fe941eeca1a5170967d5eb7ce83d98b1f1ccc028d19610e731e23 0.600000000000 1621216 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": 1137691, "vin": [ { "gen": { "height": 1137681 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e65bcbfdd03fe941eeca1a5170967d5eb7ce83d98b1f1ccc028d19610e731e23" } } ], "extra": [ 1, 130, 134, 144, 210, 26, 147, 47, 44, 105, 209, 141, 250, 85, 186, 179, 87, 27, 218, 234, 4, 190, 186, 206, 176, 144, 21, 217, 165, 203, 118, 155, 147, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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