Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6aac474a8d81d04cb6158bdc3b7e4e35fe706359f4afefdf52ad3b12673b43a

Tx prefix hash: fc6915fa2ed9a8e2ca40a18b14cef75649526e59d78b6798cf990e86b35cb43c
Tx public key: 781ec2e5a922a4326808e8d5bbe1d95c391b8472f6acedaf20c0a8af64b3f2ad
Timestamp: 1701979544 Timestamp [UCT]: 2023-12-07 20:05:44 Age [y:d:h:m:s]: 01:192:22:10:40
Block: 908160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398953 RingCT/type: yes/0
Extra: 01781ec2e5a922a4326808e8d5bbe1d95c391b8472f6acedaf20c0a8af64b3f2ad021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.601019962000 dcy

stealth address amount amount idx
00: 64733990587c1fd7dfd4b7f148a51fa34768db378a987f3aa72d20a5fb2e8c7e 0.601019962000 1365185 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": 908170, "vin": [ { "gen": { "height": 908160 } } ], "vout": [ { "amount": 601019962, "target": { "key": "64733990587c1fd7dfd4b7f148a51fa34768db378a987f3aa72d20a5fb2e8c7e" } } ], "extra": [ 1, 120, 30, 194, 229, 169, 34, 164, 50, 104, 8, 232, 213, 187, 225, 217, 92, 57, 27, 132, 114, 246, 172, 237, 175, 32, 192, 168, 175, 100, 179, 242, 173, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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