Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc714f0800f3acb90e6cc9b409fd0d4f2587fe56e56fe1254db39c2a2f3480d3

Tx prefix hash: d0675da556cc80b7fff605a6fc0046cd68651f0314c99bfbf119255a32d1e930
Tx public key: 304d491d7b114ac6d468b1fd6545bdc9102c8d7934a8a5934838622a541a2f35
Timestamp: 1585085561 Timestamp [UCT]: 2020-03-24 21:32:41 Age [y:d:h:m:s]: 05:050:14:22:38
Block: 87914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1194094 RingCT/type: yes/0
Extra: 01304d491d7b114ac6d468b1fd6545bdc9102c8d7934a8a5934838622a541a2f35021100000011d81c26c0000000000000000000

1 output(s) for total of 313.854004433000 dcy

stealth address amount amount idx
00: add6041afca41756afda45d71acd9c89cdc5b7b3ecbbd22bf48f62470bd9b083 313.854004433000 158308 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": 87924, "vin": [ { "gen": { "height": 87914 } } ], "vout": [ { "amount": 313854004433, "target": { "key": "add6041afca41756afda45d71acd9c89cdc5b7b3ecbbd22bf48f62470bd9b083" } } ], "extra": [ 1, 48, 77, 73, 29, 123, 17, 74, 198, 212, 104, 177, 253, 101, 69, 189, 201, 16, 44, 141, 121, 52, 168, 165, 147, 72, 56, 98, 42, 84, 26, 47, 53, 2, 17, 0, 0, 0, 17, 216, 28, 38, 192, 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