Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a67f623a269478620ebe81962248367a23aaf5c9d05b7840e7b7b7f2fc1fe4db

Tx prefix hash: 8f6279a37ef95050d985685dd14247c84199494e100c7f522aac12fd7b002475
Tx public key: b6944d5f211ff03b49e73371b124fc9b051ab12cc7c097f3ed9c2e59b5ac9617
Timestamp: 1718469813 Timestamp [UCT]: 2024-06-15 16:43:33 Age [y:d:h:m:s]: 00:224:13:26:48
Block: 1044876 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160644 RingCT/type: yes/0
Extra: 01b6944d5f211ff03b49e73371b124fc9b051ab12cc7c097f3ed9c2e59b5ac9617021100000001b428b0c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4f0e95b57e2af7aee4f20b72fadc362043ab9077f7a6bf7d8bf1dd29ff4e89b 0.600000000000 1514305 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": 1044886, "vin": [ { "gen": { "height": 1044876 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4f0e95b57e2af7aee4f20b72fadc362043ab9077f7a6bf7d8bf1dd29ff4e89b" } } ], "extra": [ 1, 182, 148, 77, 95, 33, 31, 240, 59, 73, 231, 51, 113, 177, 36, 252, 155, 5, 26, 177, 44, 199, 192, 151, 243, 237, 156, 46, 89, 181, 172, 150, 23, 2, 17, 0, 0, 0, 1, 180, 40, 176, 196, 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