Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfbd8a37e11a75a5f270432ab600ee1b714a3b54babd0fd271505e78d4ae78be

Tx prefix hash: d3dcc9cdc4430ca545e97094f4df7f8b673ceffa45df9105d75d9b78f1840e54
Tx public key: 9a874b75e5f7e5bc783183f5336fd5fc592cdcdbae802a3d72e8ecc8625910ff
Timestamp: 1589363695 Timestamp [UCT]: 2020-05-13 09:54:55 Age [y:d:h:m:s]: 04:348:05:18:34
Block: 100495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1168733 RingCT/type: yes/0
Extra: 019a874b75e5f7e5bc783183f5336fd5fc592cdcdbae802a3d72e8ecc8625910ff02110000004d45705818000000000000000000

1 output(s) for total of 285.139881353000 dcy

stealth address amount amount idx
00: c67b1ded3d5f095dc5d3c7946b73cb45a4c15576e8c19198c71f8ec4000ffd41 285.139881353000 177039 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": 100505, "vin": [ { "gen": { "height": 100495 } } ], "vout": [ { "amount": 285139881353, "target": { "key": "c67b1ded3d5f095dc5d3c7946b73cb45a4c15576e8c19198c71f8ec4000ffd41" } } ], "extra": [ 1, 154, 135, 75, 117, 229, 247, 229, 188, 120, 49, 131, 245, 51, 111, 213, 252, 89, 44, 220, 219, 174, 128, 42, 61, 114, 232, 236, 200, 98, 89, 16, 255, 2, 17, 0, 0, 0, 77, 69, 112, 88, 24, 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