Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a47762fd22abad287f57cb284114dea1721e8417634489adc14b714c29187928

Tx prefix hash: 47c9429519e5b0d4e34fb1d4ae93f1a469e084522dec48ccfca67108e238f7f0
Tx public key: a213055dfc8c4d7ba985f93824551a1b324796995c833e6f375e27d94410356a
Timestamp: 1704153029 Timestamp [UCT]: 2024-01-01 23:50:29 Age [y:d:h:m:s]: 01:322:08:56:26
Block: 926164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 489240 RingCT/type: yes/0
Extra: 01a213055dfc8c4d7ba985f93824551a1b324796995c833e6f375e27d94410356a0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ac5546197c210d33e1f0d180343967c1e5d6c254660651bbb8a9e055693a6c6 0.600000000000 1383938 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": 926174, "vin": [ { "gen": { "height": 926164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ac5546197c210d33e1f0d180343967c1e5d6c254660651bbb8a9e055693a6c6" } } ], "extra": [ 1, 162, 19, 5, 93, 252, 140, 77, 123, 169, 133, 249, 56, 36, 85, 26, 27, 50, 71, 150, 153, 92, 131, 62, 111, 55, 94, 39, 217, 68, 16, 53, 106, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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