Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70df0f10a2f6be00bf864cd7e7c5792acfa96585896b6eedf83d65be22e1f335

Tx prefix hash: f7acc6c8e621957d624629e33905cc746438b7b451f5203da7bb6668a7e6ed1a
Tx public key: 2144fdf9fc13fc1fade94dea4e9828f9cc009815cdf782fcd9931cb2baa9cacc
Timestamp: 1711742433 Timestamp [UCT]: 2024-03-29 20:00:33 Age [y:d:h:m:s]: 01:229:14:05:15
Block: 989117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 422759 RingCT/type: yes/0
Extra: 012144fdf9fc13fc1fade94dea4e9828f9cc009815cdf782fcd9931cb2baa9cacc0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a6a2554baad722037268cba37807d8f8fd6063b0e44f58e296c4318d2a7c3f3 0.600000000000 1449412 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": 989127, "vin": [ { "gen": { "height": 989117 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a6a2554baad722037268cba37807d8f8fd6063b0e44f58e296c4318d2a7c3f3" } } ], "extra": [ 1, 33, 68, 253, 249, 252, 19, 252, 31, 173, 233, 77, 234, 78, 152, 40, 249, 204, 0, 152, 21, 205, 247, 130, 252, 217, 147, 28, 178, 186, 169, 202, 204, 2, 17, 0, 0, 0, 1, 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