Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fc9241af66a33bdbdab2d312658e84a4ce8001a85c678e24409c290b839c70f

Tx prefix hash: 48d74e0f724ca2b66bd583c93f493d925750d18ef905f4ba72088be43e64f1da
Tx public key: d36dcaa40e6e340730dc84a600101010bde3d248ac2fa9345170019a6494f08e
Timestamp: 1660869185 Timestamp [UCT]: 2022-08-19 00:33:05 Age [y:d:h:m:s]: 02:298:13:05:30
Block: 568878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 734594 RingCT/type: yes/0
Extra: 01d36dcaa40e6e340730dc84a600101010bde3d248ac2fa9345170019a6494f08e02110000000575e3f0e9000000000000000000

1 output(s) for total of 7.999652799000 dcy

stealth address amount amount idx
00: 01f6bbaa70dc7e193e32ff0b6c06ee6aac17fc1aa53d94eb7fd8f22c528a18f4 7.999652799000 1002005 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": 568888, "vin": [ { "gen": { "height": 568878 } } ], "vout": [ { "amount": 7999652799, "target": { "key": "01f6bbaa70dc7e193e32ff0b6c06ee6aac17fc1aa53d94eb7fd8f22c528a18f4" } } ], "extra": [ 1, 211, 109, 202, 164, 14, 110, 52, 7, 48, 220, 132, 166, 0, 16, 16, 16, 189, 227, 210, 72, 172, 47, 169, 52, 81, 112, 1, 154, 100, 148, 240, 142, 2, 17, 0, 0, 0, 5, 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