Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2635ea50c1f82d2f518338c1d0d146b8821888a2b6797ed3690daec9f99d8cd4

Tx prefix hash: 50d167d10ecd39d3162de154ac449bb8088eec284e4cd9224271d03b213c57ab
Tx public key: 588538ce74eb2e99e2eb24fe2816ec00fb942d6d273095ca28b6d5698cfa7a2e
Timestamp: 1581951150 Timestamp [UCT]: 2020-02-17 14:52:30 Age [y:d:h:m:s]: 04:318:05:03:42
Block: 66934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1119724 RingCT/type: yes/0
Extra: 01588538ce74eb2e99e2eb24fe2816ec00fb942d6d273095ca28b6d5698cfa7a2e0211000000040aca7173000000000000000000

1 output(s) for total of 368.316080664000 dcy

stealth address amount amount idx
00: a6ebe654aaf92f7cf4611972342449c061cc24481ab8f3ce79ddbf10eee0b2f2 368.316080664000 123195 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": 66944, "vin": [ { "gen": { "height": 66934 } } ], "vout": [ { "amount": 368316080664, "target": { "key": "a6ebe654aaf92f7cf4611972342449c061cc24481ab8f3ce79ddbf10eee0b2f2" } } ], "extra": [ 1, 88, 133, 56, 206, 116, 235, 46, 153, 226, 235, 36, 254, 40, 22, 236, 0, 251, 148, 45, 109, 39, 48, 149, 202, 40, 182, 213, 105, 140, 250, 122, 46, 2, 17, 0, 0, 0, 4, 10, 202, 113, 115, 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