Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e695f86ac033e4cb708f36c690f64962a2e796ed27ab47f1f88e632b767342e

Tx prefix hash: 2bca1f7e5636ebd0a72e6c33effd0f52d44ecba3e64e93aa3a4a0d47c9c09301
Tx public key: 31b359c5547bf218e0b854fde5b8f561df5aeea1609fa02bf34a86913cd44349
Timestamp: 1635070480 Timestamp [UCT]: 2021-10-24 10:14:40 Age [y:d:h:m:s]: 03:027:01:49:28
Block: 359439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 797662 RingCT/type: yes/0
Extra: 0131b359c5547bf218e0b854fde5b8f561df5aeea1609fa02bf34a86913cd4434902110000001cf60c5d7e000000000000000000

1 output(s) for total of 39.543174309000 dcy

stealth address amount amount idx
00: 04e639281f72e182ff1d396a36718444f08b171d426626dafbf5cf83b0b5e351 39.543174309000 731944 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": 359449, "vin": [ { "gen": { "height": 359439 } } ], "vout": [ { "amount": 39543174309, "target": { "key": "04e639281f72e182ff1d396a36718444f08b171d426626dafbf5cf83b0b5e351" } } ], "extra": [ 1, 49, 179, 89, 197, 84, 123, 242, 24, 224, 184, 84, 253, 229, 184, 245, 97, 223, 90, 238, 161, 96, 159, 160, 43, 243, 74, 134, 145, 60, 212, 67, 73, 2, 17, 0, 0, 0, 28, 246, 12, 93, 126, 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