Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ac45bd637e5c36fee17d01c03b79113d211f5a16a41329afe2ce10d15a4ba86

Tx prefix hash: 10cd576da384ea54fd06908cc85f2cc1dd863a03c1e3ce36f30bced0ea44f5c6
Tx public key: cd653b15cd2f2e4c46ae993923d9cc40d5d8a273161ec80bf12270112c39759d
Timestamp: 1638747508 Timestamp [UCT]: 2021-12-05 23:38:28 Age [y:d:h:m:s]: 03:098:23:11:41
Block: 389278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 849434 RingCT/type: yes/0
Extra: 01cd653b15cd2f2e4c46ae993923d9cc40d5d8a273161ec80bf12270112c39759d02110000000237cb3088000000000000000000

1 output(s) for total of 31.489136836000 dcy

stealth address amount amount idx
00: ffd28411d90cd794b8d4b2385c5c478eaee973ca59b3b25fe60857e4a55dd317 31.489136836000 784361 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": 389288, "vin": [ { "gen": { "height": 389278 } } ], "vout": [ { "amount": 31489136836, "target": { "key": "ffd28411d90cd794b8d4b2385c5c478eaee973ca59b3b25fe60857e4a55dd317" } } ], "extra": [ 1, 205, 101, 59, 21, 205, 47, 46, 76, 70, 174, 153, 57, 35, 217, 204, 64, 213, 216, 162, 115, 22, 30, 200, 11, 241, 34, 112, 17, 44, 57, 117, 157, 2, 17, 0, 0, 0, 2, 55, 203, 48, 136, 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