Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f75fe30ca1b00b278a7e86e6091de212177ead19203aaa676c4e3dcf3e96d4d4

Tx prefix hash: dd5e2952303154d94ecbe5b4e3fbe483be589000c5ab21bfabd62c4651ad5c48
Tx public key: 00ffd2da6e5f24cba97db3aeae4e3514ab690de73df89df88aa0833dcdbb0e2b
Timestamp: 1580488810 Timestamp [UCT]: 2020-01-31 16:40:10 Age [y:d:h:m:s]: 05:042:03:51:39
Block: 56100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1181821 RingCT/type: yes/0
Extra: 0100ffd2da6e5f24cba97db3aeae4e3514ab690de73df89df88aa0833dcdbb0e2b021100000004ff58ae94000000000000000000

1 output(s) for total of 400.053648764000 dcy

stealth address amount amount idx
00: a3b05c7c08d4aaef27719c6e9a229f6eab6078f0b0cda6917a7c1cea1fe35520 400.053648764000 103432 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": 56110, "vin": [ { "gen": { "height": 56100 } } ], "vout": [ { "amount": 400053648764, "target": { "key": "a3b05c7c08d4aaef27719c6e9a229f6eab6078f0b0cda6917a7c1cea1fe35520" } } ], "extra": [ 1, 0, 255, 210, 218, 110, 95, 36, 203, 169, 125, 179, 174, 174, 78, 53, 20, 171, 105, 13, 231, 61, 248, 157, 248, 138, 160, 131, 61, 205, 187, 14, 43, 2, 17, 0, 0, 0, 4, 255, 88, 174, 148, 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