Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cd674024ea7024832400b883b63185c125f8285d3ac9c66342c5c98a1942252

Tx prefix hash: 8af90bae1a61fbe51b6b510c52860f3be3766638fa03e6376352224bf699ef8c
Tx public key: e1a1d98e87b1a16365c424d6d464285201d11d60933e1f9095c057f43270ffab
Timestamp: 1697396226 Timestamp [UCT]: 2023-10-15 18:57:06 Age [y:d:h:m:s]: 01:099:05:30:38
Block: 870365 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332128 RingCT/type: yes/0
Extra: 01e1a1d98e87b1a16365c424d6d464285201d11d60933e1f9095c057f43270ffab021100000011faf35c9c000000000000000000

1 output(s) for total of 0.801898638000 dcy

stealth address amount amount idx
00: a0a79e9e054bad8a39bbaaa79fc531c3b8ec1c685ed32821e5049b4dc2f8318e 0.801898638000 1325244 of 0

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": 870375, "vin": [ { "gen": { "height": 870365 } } ], "vout": [ { "amount": 801898638, "target": { "key": "a0a79e9e054bad8a39bbaaa79fc531c3b8ec1c685ed32821e5049b4dc2f8318e" } } ], "extra": [ 1, 225, 161, 217, 142, 135, 177, 161, 99, 101, 196, 36, 214, 212, 100, 40, 82, 1, 209, 29, 96, 147, 62, 31, 144, 149, 192, 87, 244, 50, 112, 255, 171, 2, 17, 0, 0, 0, 17, 250, 243, 92, 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