Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd109314fab3ab151114e530375d83f14b36722768666182a1b4afc476e283ca

Tx prefix hash: 1bac96d4bf89239799f582cdab25b5edf4703827085a711c54b1236c4b44941b
Tx public key: e978c41f32ecd78f7a0f02eafb4832b2946e499ff4db1ccc102db71596452392
Timestamp: 1693227351 Timestamp [UCT]: 2023-08-28 12:55:51 Age [y:d:h:m:s]: 02:074:08:45:30
Block: 835764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 572874 RingCT/type: yes/0
Extra: 01e978c41f32ecd78f7a0f02eafb4832b2946e499ff4db1ccc102db7159645239202110000000375e3f0e9000000000000000000

1 output(s) for total of 1.044159883000 dcy

stealth address amount amount idx
00: 47f6b1de10fe9bbb001431c2e232f3fdac1bf95ee7d445726e5c71e3be54dfd2 1.044159883000 1288332 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": 835774, "vin": [ { "gen": { "height": 835764 } } ], "vout": [ { "amount": 1044159883, "target": { "key": "47f6b1de10fe9bbb001431c2e232f3fdac1bf95ee7d445726e5c71e3be54dfd2" } } ], "extra": [ 1, 233, 120, 196, 31, 50, 236, 215, 143, 122, 15, 2, 234, 251, 72, 50, 178, 148, 110, 73, 159, 244, 219, 28, 204, 16, 45, 183, 21, 150, 69, 35, 146, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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