Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcff47b08c90c8bc446862dc88850efdc6bdf3b35c3d08c3e080e63f823c1e8a

Tx prefix hash: 655a71feadf2460bda5494ff9774a3ea4b9f02307b404fea608a3084c8ac77f5
Tx public key: 9b24e27eb7a70946455416188a0049a40ded3a6d363acad15b41b2157c16670e
Timestamp: 1583431930 Timestamp [UCT]: 2020-03-05 18:12:10 Age [y:d:h:m:s]: 04:340:18:25:18
Block: 76758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1138035 RingCT/type: yes/0
Extra: 019b24e27eb7a70946455416188a0049a40ded3a6d363acad15b41b2157c16670e02110000000c4ac5aa02000000000000000000

1 output(s) for total of 341.719432881000 dcy

stealth address amount amount idx
00: a187b6b94f0910871efe6d825e8b09c131f63913e2a3a72f651845c0749231c4 341.719432881000 141326 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": 76768, "vin": [ { "gen": { "height": 76758 } } ], "vout": [ { "amount": 341719432881, "target": { "key": "a187b6b94f0910871efe6d825e8b09c131f63913e2a3a72f651845c0749231c4" } } ], "extra": [ 1, 155, 36, 226, 126, 183, 167, 9, 70, 69, 84, 22, 24, 138, 0, 73, 164, 13, 237, 58, 109, 54, 58, 202, 209, 91, 65, 178, 21, 124, 22, 103, 14, 2, 17, 0, 0, 0, 12, 74, 197, 170, 2, 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